<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml11.xsd"
     xml:lang="en">
  <head>
    <title>Information Center for ARM</title>
    <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8" />
    <link type="text/css" rel="stylesheet" media="all" href="file://$TOOLKIT_DIR$/doc/infocenter/style/ewic.css" />
  </head>
  <body>
  <div id="topbanner"></div>
  <div id="titlebanner_small">
    <h2>Information Center for ARM</h2>
  </div>
  <div class="breadcrumb"><a href="$TOOLKIT_DIR$/doc/infocenter/index.ENU.html">Information Center for ARM</a> | EXAMPLES</div>
  <div class="mainblock">
   <h2>Example description</h2>

   <pre>  <!--Insert readme.txt-->

CAN_AFLUT_dynamic
 
Purpose:
 
  This is a simple example for CAN peripheral to test functions that support add/remove AFLUT entry dynamically.
  We use 2 CAN peripheral CAN1 and CAN2 in the same kit to test CAN operation.
  This example supports FullCAN and Group ID Frame Format.
  First, we send 10 messages, include:
    - 5 messages (0,2,4,6,8) have ID in AFLUT --> will be received 
    - 5 messages (1,3,5,7,9) don't have ID in AFLUT --> will be ignored
  Then, we change AFLUT by load and remove entries in AFLUT and re-send messages
    - 5 messages (1,3,5,7,9) have ID in ALFUT --> will be received 
    - 5 messages (0,2,4,6,8) don't have ID in AFLUT --> will be ignored

Hardware configuration:
    This example tested on Keil MCB2300 platform v4.0 with LPC1768
    - CAN1-Pin2 connects to CAN2-Pin2
    - CAN1-Pin7 connects to CAN2-Pin7	
Running mode:
    This example can run on RAM mode with a debugger or run on FLASH after burning.
Note:
    FullCAN Object must be read from FullCAN Object Section next to AFLUT
      
-----------------------------------------------------------------------------------
CAN_test_AFLUT     
  
Purpose:
  This is a simple example for CAN peripheral to test full Acceptance Filter operation.
  We use 2 CAN peripheral CAN1 and CAN2 in the same kit to test CAN operation.
  This example supports FullCAN and Group ID Frame Format.
  To test AF mode: we setup a simple AF Lookup Table with 5 sections:
    - FullCAN Identifier Frame Format Section
    - Explicit Standard Frame Format Identifier Section
    - Group of Standard Frame Format Identifier Section
    - Explicit Extended Frame Format Identifier Section
    - Group of Extended Frame Format Identifier Section
    and initialize 10 messages, include:
    - 5 messages have ID exit in 5 sections
    - 5 messages have ID not exit in AF Lookup Table to check AF operation 
        
Hardware configuration:
    This example tested on Keil MCB2300 platform v4.0 with LPC1768
    - CAN1-Pin2 connects to CAN2-Pin2
    - CAN1-Pin7 connects to CAN2-Pin7	
Running mode:
    This example can run on RAM mode with a debugger or run on FLASH after burning.
Note:
    - FullCAN Object must be read from FullCAN Object Section next to AFLUT

-----------------------------------------------------------------------------------
CAN_test_bypass_mode
  
Purpose:
  This is a simple example for CAN peripheral to test Bypass mode
  We use 2 CAN peripheral CAN1 and CAN2 in the same kit to test CAN operation.
  To test Bypass mode: we send infinite messages to CAN2.
  After each transfer, we increase ID message and its data to continue transmit.
  This example tested on Keil MCB2300 platform v4.0 with LPC1768
  
Hardware configuration:
   This example tested on Keil MCB2300 platform v4.0 with LPC1768
   - CAN1-Pin2 connects to CAN2-Pin2
   - CAN1-Pin7 connects to CAN2-Pin7
Running mode:
   This example can run on RAM mode with a debugger or on FLASH after burning.
Note:
    - FullCAN Object must be read from FullCAN Object Section next to AFLUT

-----------------------------------------------------------------------------------
CAN_test_two_kit

Purpose:
  This is a simple example to test CAN transfer data between two board
  
Hardware configuration:
    This example runs on IAR-LPC1768-SK or Keil MCB2300 platform v4.0 with LPC1768
    IAR-LPC1768-SK configuration
      - CAN_H on the firts board conected to CAN_H on the second doard
      - CAN_L on the firts board conected to CAN_L on the second doard
      - GND on the firts board conected to GND on the second doard
    KEIL board configuration
      - CAN1-Pin2 on the first board connects to CAN1-Pin2 on the second board.
      - CAN1-Pin7 on the first board connects to CAN1-Pin7 on the second board.		
Running mode:
    Run the transmit programe on first board on FLASH mode.
    Run the receive programe on second board on RAM mode with debugger.
Note:
    - If you want to chose Transmit or Receive programe, check via macro "CAN_TRANSMIT"   


All examples Using UART0 with configuration:
		- 115200bps 
		- 8 data bits
		- No parity 
		- 1 stop bit 
		- No flow control   
  </pre>

  </div>
  </body>
</html>

